MSI move 2018-11-30 version in stable folder#4768
MSI move 2018-11-30 version in stable folder#4768jhendrixMSFT merged 1 commit intoAzure:masterfrom wendyNEU:RemoveToStableFolder
Conversation
|
If you're a MSFT employee, click this link |
Automation for azure-sdk-for-jsNothing to generate for azure-sdk-for-js |
Automation for azure-sdk-for-pythonNothing to generate for azure-sdk-for-python |
Automation for azure-sdk-for-rubyNothing to generate for azure-sdk-for-ruby |
Automation for azure-sdk-for-javaNothing to generate for azure-sdk-for-java |
Automation for azure-sdk-for-nodeNothing to generate for azure-sdk-for-node |
Automation for azure-sdk-for-goThe initial PR has been merged into your service PR: |
|
I found another pr already sent to move 2018-11-30 in stable folder #4743 |
|
If you're a MSFT employee, click this link |
|
Can one of the admins verify this patch? |
|
This pr is to move 2018-11-30 version folder to stable folder |
|
@wendyNEU just to confirm, this API version is deployed and publicly available? |
|
OK based on comments in the original PR deployment started last month and presumably finished since Amar merged the change to master. |
Latest improvements:
MSFT employees can try out our new experience at OpenAPI Hub - one location for using our validation tools and finding your workflow.
Contribution checklist:
ARM API Review Checklist
Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs.
Please follow the link to find more details on API review process.
autorest generate code

autorest validator

validate with oav

validate with OpenAPI Hub
